Open
Conversation
Member
|
Hey @alxckn, thanks a lot for starting this and sorry for the delay. I was supposed to work on sharding at the end of last year but in the end I switched to work on something else and have been focused on other stuff since then. I'll look into this soon. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #353
This is a proposal to add multisharding as a supported configuration option for Solid Queue. It makes it possible to easily migrate incrementally an application from one to multiple shards as changing the
connects_toconfiguration will not change any of the default behavior of Solid Queue.This introduces 2 ways to determine which shard to enqueue a job to:
queue_adapteron a job, so that a given job class would be assigned to a given shard (ensuring full compatibility with some other Solid Queue features such as concurrency control)shard_selection_lambdato have complete control over shard selection logic when enqueueing jobsBy configuring the
active_sharddynamically (for instance using an environment variable), it is possible to start workers, dispatchers and schedulers that will consume each shard.